Network stress test

ABSTRACT

A method of conducting a network stress test includes providing a first client in communication with a first server via a client-server relationship. The method also includes setting a first frequency as a set frequency. The method further includes sending a first request from the first client to the first server at the set frequency. Additionally, the method includes sending a first response from the first server to the first client. The method also includes measuring a first elapsed time between the first request and the first response, and comparing the first elapsed time to a communication threshold.

FIELD OF THE DISCLOSURE

The present disclosure relates to a network stress test for use in Building Automation and Control Networks (BACnet) Protocol or other similar protocol. The network stress test may identify a breaking point of a single device on the protocol.

BACKGROUND

Building Automation and Control Networks (BACnet) is a commonly used protocol standard for Building Management Systems (BMS) that allows for building automation and may be used with a variety of building sub-systems (e.g., HVAC, lighting, fire detection, security, etc.). BACnet allows different sub-systems made by different manufacturers to communicate with one another over a standardized network. This allows building owners to implement a wide range of sub-systems, and allows these sub-systems to interact with one another. This may be useful for energy management systems (e.g., turning on or off the HVAC system based on an occupancy sensor in a light system).

Protocols like BACnet generally utilize a client-server software model in order to communicate between the different building sub-systems. Some sub-systems (e.g., HVAC) have a large memories, and request data from or poll other sub-systems (e.g., lighting), which may have smaller memories. The client is the sub-system requesting the data, and the server is the sub-system providing the data. From the server's prospective, the client-server relationship may be one-to-one (e.g., there is one client requesting data from an individual server), or the client-server relationship may be many-to-one (e.g., there are multiple clients requesting data from the individual server). Depending on the type of client (e.g., the individual building system) or the data required, different clients may poll the individual server at different rates.

The volume of clients and the speed at which each client polls places stress on the server. A combination of a large number of clients polling an individual server and individual clients polling too quickly may cause the server to lag, buffer, or fail. If this happens, the server may be unable to communicate with the client(s), and the client(s) may be unable to extract the requisite data they need. This may cause a system wide slowdown or failure across the entire building. This slowdown or failure may effect inhabitant discomfort and/or inhabitant safety.

SUMMARY

In one embodiment, a method of conducting a network stress test may include providing a first client in communication with a first server via a client-server relationship. The method may also include setting a first frequency as a set frequency. The method may further include sending a first request from the first client to the first server at the set frequency. Additionally, the method may include sending a first response from the first server to the first client. The method also includes measuring a first elapsed time between the first request and the first response, and comparing the first elapsed time to a communication threshold.

In another embodiment, a method of conducting a network stress test on a BACnet protocol may include providing a first client in communication with a first server via a client-server relationship. The method may also include providing a measurement system in communication with the first client and the first server. The method may further include sending a first request from the first client to the first server at the set frequency. Additionally, the method may include sending a first response from the first server to the first client. The method may also include measuring a first elapsed time between the first request and the first response with the measurement system, and displaying the first elapsed time.

In yet another embodiment, a method of determining performance degradation on a BACnet protocol may include providing a first client in communication with a first server via a client-server relationship, and providing a measurement system in communication with the first client and the first server. The method may also include repeatedly sending a first request from the first client to the first server at a set frequency, and sending a first response from the first server to the first client for each first request. Additionally, the method may include measuring a first elapsed time between each successive first request and first response, and measuring a second elapsed time between an initial request and a final response. The method may also include comparing the first elapsed time to a first threshold, and comparing the second elapsed time to a second threshold. Finally, the method may include increasing the set frequency when the second elapsed time exceeds the second threshold, and halting sending the first request from the first client to the first server at the set frequency when the first elapsed time exceeds the first threshold.

Other aspects of the disclosure will become apparent by consideration of the detailed description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a schematic view of a single client system running on the BACnet protocol according to a number of embodiments.

FIG. 2 depicts a schematic view of a multiple client system running on the BACnet protocol according to a number of embodiments.

FIG. 3 depicts a schematic view of a message testing flow according to a number of embodiments.

FIG. 4 depicts a flow diagram of a first test cycle which may be used with the single client system embodiments depicted in FIG. 1.

FIG. 5 depicts a flow diagram of a second test cycle which may be used with the multiple client system embodiments depicted in FIG. 2.

DETAILED DESCRIPTION

Before any embodiments are explained in detail, it is to be understood that the disclosure is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. The disclosure is capable of other embodiments and of being practiced or of being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. Use of “including” and “comprising” and variations thereof as used herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Use of “consisting of” and variations thereof as used herein is meant to encompass only the items listed thereafter and equivalents thereof. Unless specified or limited otherwise, the terms “mounted,” “connected,” “supported,” and “coupled” and variations thereof are used broadly and encompass both direct and indirect mountings, connections, supports, and couplings.

In general, the present disclosure relates to a network stress test for determining failure points in the BACnet Protocol. The network stress test may identify a maximum amount of traffic an individual device using the BACnet Protocol can withstand without causing a network failure.

As shown in FIG. 1, the BACnet protocol may be organized in a client-server relationship. The illustrated embodiment depicts a single client system 10 according to a number of embodiments. A client 100 may be a larger device or sub-system in the overall BMS. Clients 100 may have large internal memories or processors, and may be able to process large amounts of data. Through operation, the client 100 may produce and collect data that can be used in self-regulating the client 100 (e.g., changing an operating mode of the client 100). For example, an HVAC system may include a temperature sensor that controls if and when heating and cooling systems are turned on or off.

Clients 100 may also collect data from servers 105 concurrently running on the BACnet protocol. A server 105 may be a smaller device or sub-system in the overall BMS. Compared to clients 100, servers 105 have smaller internal memories or processors and may be unable to process the same volume of data as clients 100. Clients 100 may request data from servers 105 to further assist in regulation. For example an HVAC system may request data from a lighting fixture, and heat or cool a room based on a signal received from the lighting fixture (e.g., whether an occupancy sensor senses a person in a room).

To acquire the data from the server 105, the client 100 may send a request 110. By sending a request 110, the client 100 may be requesting a specific piece of information from the server 105 (e.g., whether the light fixture is on). The server 105 may answer a request 110 by sending a response 115 to a client 100. In some embodiments, the process of polling (i.e., sending requests 110 and responses 115 between clients 100 and servers 105) may be continuous at a given frequency t_(c) (i.e., a number of requests 110 per minute) while the client 100 and the server 105 are on. In other embodiments, polling may take place at varying frequencies for a given client 100 and server 105.

As depicted in FIG. 2, a multiple client system 20 may include multiple clients 100 throughout the BACnet protocol that may be in communication with a single server 105. Each client 100 may make separate requests 110 to the server 105, and the server 105 may then answer each separate request 110. In some embodiments, each client 100 may make an identical, but separate request 110 (i.e., each client 100 requests the same piece of information). In other embodiments, some clients 100 may make unique requests 110 from other clients 100 (i.e., each client 100 asks for different pieces of information). Individual requests 110 may each be made at a constant time interval (e.g., the time t_(c) for every client 100 may be the same). Each client 100 may also make requests 110 at different time intervals (e.g., the time t_(c) for some clients 100 may be different).

To control the volume of data reaching the server 105, a switch 120 (e.g., a layer 2 network switch) may be positioned between the clients 100 and the server 105. The switch 120 may allow only a certain number of clients 100 to make a request 110 at a time, by allowing only a certain number of requests 110 to proceed to the server 105. In such a case, the switch 120 may block all requests 110 over the certain number from reaching the server 105 until the current certain number of requests 110 have been resolved (e.g., with a response 115).

In both the single client system 10 (see e.g., FIG. 1) and the multiple client system 20 (see e.g., FIG. 2), a point may exist at which the server 105 is unable to provide a suitable response 115 to the request 110 from the client 100 (e.g., a elapsed or response time t_(res) between the request 110 and the response 115 exceeds a user defined communication threshold). In the multiple client system 20, a threshold of acceptable elapsed times t_(res) between a request 110 and a response 115 may differ between different clients 110 (e.g., in some clients 100 the response time t_(res) may be critical, while in other clients 100 the response time may not be critical). The communication threshold in the multiple client system 20 may therefore be linked to the most critical client 100 (e.g., the client with the fastest required response time t_(res) may, as a practical matter, may set the response time requirements for the server). For example, clients 100 responsible for life safety functions may require a more timely response time t_(res) than clients 100 not responsible for life safety functions.

Understanding how and when the response time t_(res) the communication threshold is important, particularly to manufacturers of BACnet servers 105. Manufacturers need to understand what polling frequency t_(c) and how many clients 100 may cause performance degradation (i.e., exceeding the communication threshold) for their server 105.

As shown in FIGS. 1 and 2, capture software 125 may be incorporated into the network. The capture software 125 may record requests 110 by the client 100, as well as responses 115 by the servers 105. The capture software 125 may record the type of request 110 and response 115 (e.g., what the client 100 is asking for and what the server 105 provides). The capture software 125 may also record elapsed time t_(res) a request 110 and a response 115. In some cases, this record of requests 110 and responses 115 may be downloadable or shareable over a centralized network. In the multiple client system 20, capture software 125 may be positioned between the switch 120 and the server 105, and may record the requests 110 and the responses 115 to and from the server 105. Records from the capture software 125 may allow a user to analyze different time intervals for responses 115 across different types of requests 110.

As depicted in FIG. 3, a client 100 may send multiple messages M to a server 105 via a request 110. In some embodiments, each message M may be the same (e.g., the client 100 may be requesting the same piece of information), while in other embodiments, different messages M may request a different piece of information. After receiving the message M, the server 105 may send the client 100 a response 115 with in a response time t_(res). The client 100 may then proceed to send the next message M (e.g., request the same or different pieces of information) after a defined rate t_(c) has elapsed. This defined rate t_(c) may be the polling rate for the given client 100. The network stress test may measure whether the server 105 has a response time t_(res) is less than the polling frequency t_(c). In a multiple client system 20, the network stress test may measure whether the server 105 has a response time t_(res) for all requests 110 that is less than the polling frequency t_(c) of the most critical client 100. This information may be important to determine if a user does not want the server 105 to get backed up and thereby become potentially unable to timely respond 115 to requests 110.

As depicted in FIG. 4, a first polling or test cycle may be used with the single client system 10 and the capture software 125 in order to determine when a communication threshold is reached. To start the first test cycle 200, a first determination as to what the communication threshold is 205 for the given client 100 (e.g., determining the slowest acceptable response time t_(res) for the particular client 100), as well as a test threshold or the total length of the test 210 (e.g., one hour). A first frequency 215 (e.g., a minimum or slowest frequency) may also be established. In a number of embodiments, the first frequency t_(c) may be one request 110 every 10 minutes. In other embodiments, the first frequency t_(c) may be more or less than one request 110 every 10 minutes. The first test cycle may be initiated by polling the server 105 at the first frequency 220. It is contemplated herein that a user or machine may establish a frequency or a response time.

After receiving the request 110, the server 105 may give a response 115, which may be recorded 225 by the capture software 125. The capture software 125 may then compare the response time t_(res) to the established communication threshold 230. If the response time is less than the threshold (e.g., if the response time t_(res) faster than the slowest allowable response time is established by the communication threshold 205), the capture software 125 may then check, within the first cycle, how long the client has been polling at the current frequency 235. If that elapsed time is less (i.e., faster) than the set length of the test, then the client may resume polling at the set frequency 220 (e.g., the first frequency t_(c)).

If the response time t_(res) less than the threshold and the first test has elapsed (e.g., is one hour has elapsed), the polling frequency 240 is increased, and resumes polling the server 105 at the new frequency t_(c). Each time the test elapses without reaching the communication threshold, increases to the polling frequency 240 may be made. In a number of embodiments, the polling frequency t_(c) may be increased in defined increments (e.g., from one request 110 every 10 minutes to one request 110 every 0.001 ms). In other embodiments, the polling frequency t_(c) may be increased between one request every 10 minutes to one request 110 every 0.001 seconds with a minimum of six steps (e.g., one message every 10 minutes, 1 minutes, 10 seconds, 1 second, 0.1 seconds, 0.01 seconds, and 0.001 seconds).

If the poll response time t_(res) is greater than the established communication threshold 230, then the first test cycle ends 245. The capture software 125 may record when the server was unable to respond under the communication threshold. This may allow a user or machine to see how long into a test and at what frequency the server was unable to respond under the communication threshold.

As shown in FIG. 5, a second polling or test cycle may be used with the multiple client system 20 and the capture software 125 in order to determine when a communication threshold is reached. To start the second test cycle 300, the communication threshold 305 may be determined for the given set of clients 100 (e.g., determining the slowest acceptable response time t_(res) for the most critical client 100), as well as a test threshold or the total length of the test 310 (e.g., one hour). A first client may subsequently added in communication with the server 315, and a first frequency 320 may be established (e.g., a minimum or slowest frequency). In a number of embodiments, the first frequency t_(c) may be one request 110 every 10 minutes. In other embodiments, the first frequency t_(c) may be more or less than one request 110 every 10 minutes. A second test cycle may be subsequently initiated by polling the server 105 at the first frequency 325.

After receiving the request 110, the server 105 may give a response 115, all of which may be recorded 330 by the capture software 125. The capture software 125 may then compare the response time t_(res) to the established communication threshold 335. If the response time t_(res) is less than the threshold (e.g., the response time t_(res) faster than the slowest allowable response is time established by the communication threshold 305), a check of how long the client has been polling at the current frequency 340 may performed. If that elapsed time t_(res) less (i.e., faster) is than the set length of the test, the client may resume polling at the set frequency 325 (e.g., the first frequency t_(c)).

If the response time t_(res) is less than the threshold and the first test has elapsed (e.g., one hour has elapsed), the polling frequency 345 may be increased, and resumes polling the server 105 may resume at the new frequency t_(c). Each time the test elapses without reaching the communication threshold, the polling frequency 345 may be increased. In a number of embodiments, the polling frequency may be increased in defined increments (e.g., from one request 110 every 10 minutes to one request 110 every 0.001 ms). In other embodiments, the polling frequency may be increased between one request every 10 minutes to one request 110 every 0.001 seconds with a minimum of six steps (e.g., one message every 10 minutes, 1 minutes, 10 seconds, 1 second, 0.1 seconds, 0.01 seconds, and 0.001 seconds).

If the poll response time t_(res) greater than the established communication threshold 335, the capture software may then check to see if the maximum number of clients for the given cycle have been reached 350. If not, one additional client 355 may be added and the test may be repeated, starting at the lowest frequency t_(c) (e.g., one request per client every 10 minutes). The switch 120 may control which client 100 is allowed to communicate with the server 105 at a given time (e.g., the clients 100 may alternate between communicating and not communicating with the server 105). If a test is completed (e.g., the time has elapsed) and the threshold was not reached, the polling frequency 345 may be increased. If the communication threshold is reached prior to completing a test, an additional client 100 may be added 355, and the tests may be repeated. Once the final client is added 355 (e.g., the total number of clients 100 being used for the second test cycle is reached), and the communication threshold is reached, the second test cycle may end 360.

After completing a test cycle, the capture software 125 may be used to determine each point where the communication threshold was reached. In light of this data, manufacturers of BACnet servers 105 may change internal performance parameters within the server 105 to improve performance characteristics (e.g., increase the frequency at which the server 105 will be unable to meet the communication threshold). Manufacturers may also provide performance requirements to a specific BMS by giving the maximum number of clients 100 an individual server 105 are enabled to communicate with at a given frequency t_(c).

It will be recognized by one of skill in the art that the methods and systems described herein are not only useful for network stress testing and preventing network faults, failures, or interruptions, but are also useful for optimizing network communications according to an administrator's desire. As a non-limiting example, a threshold or communication threshold described herein does not necessarily refer only to a point at which a network failure or fault may occur but may also refer to a communication goal selectively set or chosen by an administrator for the purpose of communication optimization such as but not limited to increasing average server response time across a network or calibrating as many clients as possible to communicate with a server. Further, it is contemplated herein that such selectively set or chosen communication thresholds may be chosen by a human administrator or by an autonomous machine administrator.

The embodiment(s) described above and illustrated in the figures are presented by way of example only and are not intended as a limitation upon the concepts and principles of the present disclosure. As such, it will be appreciated that variations and modifications to the elements and their configuration and/or arrangement exist within the spirit and scope of one or more independent aspects as described. 

What is claimed is:
 1. A method of conducting a network stress test, the method comprising: providing a first client in communication with a first server via a client-server relationship; setting a first frequency as a set frequency; sending a first request from the first client to the first server at the set frequency; sending a first response from the first server to the first client; measuring a first elapsed time between the first request and the first response; comparing the first elapsed time to a communication threshold; and, based at least upon the comparing of the first elapsed time to a communication threshold, increasing the set frequency from the first frequency to a second frequency.
 2. The method of claim 1, further comprising running the first client and the first server on a BACnet protocol.
 3. The method of claim 1, further comprising measuring a second elapsed time, and increasing the set frequency after the second elapsed time has exceeded a test threshold.
 4. The method of claim 1, further comprising providing a second client in communication with the first server via a client-server relationship; providing a switch in communication with the first client, the second client, and the first server, the switch selectively allowing communication between the first server and one of the first client and the second client; sending a second request from the second client to the first server at the set frequency; sending a second response from the first server to the second client; measuring a second elapsed time between the second request and the second response; and comparing the second elapsed time to a communication threshold.
 5. The method of claim 4, further comprising providing the second client after the first elapsed time exceeds the communication threshold.
 6. The method of claim 1, wherein the first request is repeatedly sent at the set frequency until the first elapsed time exceeds the communication threshold.
 7. A method of conducting a network stress test on a BACnet protocol, the method comprising: providing a first client in communication with a first server via a client-server relationship; providing a measurement system in communication with the first client and the first server; sending a first request from the first client to the first server at a set frequency; sending a first response from the first server to the first client; measuring a first elapsed time between the first request and the first response with the measurement system; and providing a second client in communication with a first server via a client-server relationship after the first elapsed time exceeds a communication threshold.
 8. The method of claim 7, further comprising decreasing the set frequency.
 9. The method of claim 8, further comprising sending a second request to the first server at the set frequency.
 10. The method of claim 9, further comprising measuring a second elapsed time between the sending of the first and second request and a completion by the server of the sending the first response to the first client and a sending of a second response to the second client.
 11. The method of claim 10, further comprising increasing the set frequency after the second elapsed time has exceeded a test threshold.
 12. The method of claim 10, further comprising providing a switch in communication with the first client, the second client, and the first server, the switch selectively allowing communication between the first server and one of the first client and the second client; and comparing the second elapsed time to a communication threshold.
 13. A method of determining performance degradation on a BACnet protocol, the method comprising: providing a first client in communication with a first server via a client-server relationship; providing a measurement system in communication with the first client and the first server; repeatedly sending a first request from the first client to the first server at a set frequency; sending a first response from the first server to the first client for each first request; measuring a first elapsed time between each successive first request and first response; measuring a second elapsed time between an initial request and a final response; comparing the first elapsed time to a first threshold; comparing the second elapsed time to a second threshold; increasing the set frequency when the second elapsed time exceeds the second threshold; and halting sending the first request from the first client to the first server at the set frequency when the first elapsed time exceeds the first threshold.
 14. The method of claim 13, further comprising providing a second client in communication with a first server via a client-server relationship; providing a switch in communication with the first client, the second client, and the first server, the switch selectively allowing communication between the first server and one of the first client and the second client; repeatedly sending a second request from the second client to the first server at the set frequency; sending a second response from the first server to the second client for each second request; measuring a third elapsed time between the second request and the second response; and comparing the third elapsed time to the first threshold; and halting sending the second request from the second client to the first server at the set frequency when the third elapsed time exceeds the first threshold.
 15. The method of claim 14, further comprising providing the second client after the second elapsed time exceeds the second threshold.
 16. The method of claim 14, further comprising providing a third client in communication with a first server via a client-server relationship; providing a switch in communication with the third client and the first server, the switch selectively allowing communication between the first server and one of the first client, the second client, and the third client; repeatedly sending a third request from the third client to the first server at the set frequency; sending a third response from the first server to the third client for each third request; measuring a fourth elapsed time between the third request and the third response; and comparing the fourth elapsed time to the first threshold; and halting sending the third request from the third client to the first server at the set frequency when the fourth elapsed time exceeds the first threshold.
 17. The method of claim 16, further comprising providing the third client after the first elapsed time exceeds two times the first threshold.
 18. The method of claim 16, further comprising determining the first threshold based on a characteristic of the first client.
 19. The method of claim 13, further comprising displaying the first elapsed time and the second elapsed time. 